Virtual network element provisioning

ABSTRACT

A wireless communication network comprises network circuitry which hosts a Virtual Network Function (VNF). A VNF controller instantiates the VNF in the network circuitry and transfers instantiation information for the VNF to provisioning circuitry. The provisioning circuitry receives the instantiation information for the VNF and establishes a provisioning data link to the VNF. The provisioning circuitry transfers network provisioning data to the VNF over the provisioning data link. The VNF controller de-instantiates the VNF in the network circuitry and responsively transfers de-instantiation information for the VNF to the provisioning circuitry. The provisioning circuitry receives the de-instantiation information for the VNF and terminates the provisioning data link to the VNF. The VNF controller may comprise a Network Function Virtualization Management and Orchestration (NFV MANO) computer.

RELATED CASES

This U.S. patent application is a continuation of U.S. patentapplication Ser. No. 16/404,001 that was filed on May 6, 2019 and isentitled “VIRTUAL NETWORK ELEMENT PROVISIONING.” U.S. patent applicationSer. No. 16/404,001 is hereby incorporated by reference into this UnitedStates Patent Application.

TECHNICAL BACKGROUND

Wireless user devices exchange wireless signals with wirelesscommunication networks for data services like voice-calling,internet-access, and machine communications. The wireless communicationnetworks have wireless access points that exchange the wireless signalswith the wireless user devices. The wireless access points exchangecorresponding user data and network signaling with network elements likepacket routers and network controllers. The network elements process theuser data and network signaling to deliver the data services to thewireless user devices. Popular wireless communication networks compriseLong Term Evolution (LTE) and Fifth Generation New Radio (5GNR).

In the past, each network element was typically a computer with wirelessnetworking software. For example, an older packet router might comprisea single computer having data transceivers, memory, and microprocessorsthat host an operating system and a routing applications. New networkelements have been virtualized. A virtual network element typicallycomprises a networking application, guest operating system, and virtualmachine. A computer that executes virtual network elements stillcomprises data transceivers, memory, and microprocessors. To serve thevirtual network element, the data transceivers, memory, andmicroprocessors host another operating system and virtual switches.

The virtual switches hosted by the computer communicate with the virtualmachines in the virtual network elements. Thus, a multitude of virtualnetwork elements may share the data transceivers, memory, andmicroprocessors, and operating system over the virtual machines andvirtual switches. Network virtualization adds both reliability andefficiency since the networking software is not physically tied to adedicated set of data transceivers, memory, and microprocessors.

To improve efficiency, the wireless communication networks have networkcontrollers that continuously start and stop the virtual networkelements as user demand changes. To improve reliability, the virtualswitches and machines allow data transceivers, memory, andmicroprocessors to be replaced without disrupting the operation of thevirtual network elements. A popular form of network virtualization isNetwork Function Virtualization (NFV). NFV features NFV Infrastructures(NFVIs) that host Virtual Network Functions (VNFs). The VNFs exchangeuser data and network signaling with the wireless access points todeliver the data services. NFV also has NFV Management and Orchestration(MANO) control to start and stop the VNFs.

The wireless communication networks also have provisioning systems toconfigure their virtual network elements. For example, a provisioningsystem may update the routing data in a packet router or load a newcontrol software in a network controller. The provisioning systemsestablish provisioning links to the virtual network elements when it istime to perform the provisioning and tear down the provisioning linkswhen the provisioning is complete. Unfortunately, the provisioningsystems in the wireless communication networks do not efficiently andeffectively provision their virtual network elements.

TECHNICAL OVERVIEW

A wireless communication network comprises network circuitry which hostsa Virtual Network Function (VNF). A VNF controller instantiates the VNFin the network circuitry and transfers instantiation information for theVNF to provisioning circuitry. The provisioning circuitry receives theinstantiation information for the VNF and establishes a provisioningdata link to the VNF. The provisioning circuitry transfers networkprovisioning data to the VNF over the provisioning data link. The VNFcontroller de-instantiates the VNF in the network circuitry andresponsively transfers de-instantiation information for the VNF to theprovisioning circuitry. The provisioning circuitry receives thede-instantiation information for the VNF and terminates the provisioningdata link to the VNF. The VNF controller may comprise a Network FunctionVirtualization Management and Orchestration (NFV MANO) computer.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network that provisionsvirtual network elements.

FIG. 2 illustrates the operation of a provisioning system to provisionthe virtual network elements in the wireless communication network.

FIG. 3 illustrates the operation of the wireless communication networkto provision the virtual network elements.

FIG. 4 illustrates a wireless communication network that provisionsNetwork Function Virtualization (NFV) Virtual Network Functions (VNFs).

FIG. 5 illustrates virtual network element provisioning system toprovision virtual network elements in a wireless communication network.

FIG. 6 illustrates the operation of the virtual network elementprovisioning system to provision the virtual network elements in thewireless communication network.

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 that provisionsvirtual network elements 101-105. Wireless communication network 100comprises wireless access points 107-109, network circuitry 110, VNEcontrollers 115, and provisioning system 120. Network circuitry 110stores and executes Virtual Network Elements (VNEs) 101-105.Provisioning system 120 comprises network transceiver 121 andprovisioning circuitry 122 which are coupled together.

Wireless communication network 100 serves User Equipment (UEs) with dataservices like internet, machine communications, and/or conferencing. TheUEs might be phones, computers, robots, machines, vehicles, sensors,and/or the like. The UEs and wireless access points 107-109 arewirelessly linked. Wireless access points 107-109 and VNEs 101-103 arelinked. VNEs 101-103 and VNEs 104-105 are linked, and VNEs 104-105 arelinked to various external systems like the internet or social networks(not shown). Network circuitry 110 and VNE controllers 115 are linked.VNE controllers 115 and network transceiver 121 in provisioning system120 are linked. Network transceiver 121 in provisioning system 120 andVNEs 101-105 are linked over provisioning links 131-135.

Network circuitry 110 comprises data transceivers, microprocessors,memories, bus interfaces, and software. The software comprises hardwaredrivers, operating systems, virtual components, and VNEs 101-105. Themicroprocessors retrieve and execute the software that is stored in thememories to serve the UEs with the data services. In some examples,network circuitry 110 comprises one or more Network FunctionVirtualization Infrastructures (NFVIs) and VNEs 101-105 comprise VirtualNetwork Functions (VNFs).

VNEs 101-105 may be active/instantiated or inactive/de-instantiated.Active/instantiated VNEs 101-105 have on-going microprocessors,memories, and virtual components that are allocated for their operationby network circuitry 110. Inactive/de-instantiated VNEs 101-105 do nothave microprocessors, memories, or virtual components allocated fortheir operation. Exemplary VNEs 101-105 comprise Fifth Generation Core(5GC) Access and Mobility Management Function (AMF), 5GC SessionManagement Function (SMF), 5GC User Plane Function (UPF), SoftwareDefined Network (SDN) applications, SDN controllers, SDN data machines,Long Term Evolution (LTE) Mobility Management Entity (MME), LTE ServingGateway (SGW), and/or the like. In some examples, VNEs 101-105 compriseRadio Access Network (RAN) components like Fifth Generation New Radio(5GNR) Radio Resource Control (RRC), 5GNR Service Data ApplicationProtocol (SDAP), 5GNR Packet Data Control Protocol (PDCP), LTE RRC, LTEPDCP, and/or the like.

VNE controllers 115 comprise data transceivers, microprocessors,memories, bus interfaces, and software. The software comprises hardwaredrivers, operating systems, and VNE controllers. The microprocessorsretrieve and execute the software that is stored in the memories tostart and stop the execution of VNEs 101-105 in network circuitry 110.In some examples, VNE controllers 115 comprise Network FunctionVirtualization (NFV) Management and Orchestration (MANO) computers.

In provisioning system 120, network transceiver 121 comprisestransmitters, receivers, Digital Signal Processors (DSPs), memory, businterfaces, and software. Network transceiver 121 may comprise a NetworkInterface Card (NIC), Network-On-Chip (NOC), data port circuitry, and/orthe like. Provisioning circuitry 122 comprises microprocessors, memory,bus interfaces, and software. Provisioning system 120 may comprise anindependent system or be integrated within circuitry like networkcircuitry 110 or VNE controllers 115.

In operation, the UEs wirelessly exchange data and signaling withwireless access points 107-109. Wireless access points 107-109 exchangecorresponding data and signaling with VNEs 101-103. VNEs 101-103exchange corresponding data and signaling with VNEs 104-105. VNEs104-105 exchange corresponding data and signaling with external systemslike messaging servers and enterprise computers. During theseoperations, VNE controllers 115 direct network circuitry 110 to startand stop VNEs 101-105. At any given time, VNEs 101-105 may be running oridle. In the typical situation, VNE controllers 115 mightcontemporaneously instantiate and de-instantiate thousands VNEs.

VNE controllers 115 publish network element information thatcharacterizes the VNEs that it instantiates and de-instantiatesincluding VNEs 101-105. The network element information indicatesinstantiation status and contact information. Network transceiver 121receives a version of the network element information—possibly throughintermediate systems. Network transceiver 121 transfers the networkelement information to provisioning circuitry 122. Provisioningcircuitry 122 processes the network element information to detect anyactive VNEs that do not have provisioning links and to detect anyinactive VNEs that have provisioning links. Provisioning circuitry 122maintains data structures that associate the VNEs, VNE addresses, VNElinks, VNE types, VNE regions, VNE versions, and the like. Provisioningcircuitry 122 compares incoming the network element information to itsdata structures in real-time or with high-frequency to detect the VNEsand links in a timely manner.

Provisioning circuitry 122 terminates any active provisioning links forany inactive VNEs 101-105 and updates its data structures. Terminating aprovisioning links entails clearing link context from memory andreleasing microprocessor resources. For an active VNE that does not havea provisioning link, provisioning circuitry 122 determines a networkaddress for the VNE. For example, provisioning circuitry 110 may use adomain name service to translate a VNF ID from the network elementinformation into a network address. Provisioning circuitry 122 exchangesnetwork signaling and the network address with network transceiver 121to initiate the provisioning link. Network transceiver 122 exchanges thenetwork signaling with the VNF using the network address to establishthe provisioning link.

Consider a situation where VNE 103 was just instantiated by networkcircuitry 110 under the direction of VNE controller 115. VNE 103 doesyet not have provisioning link 133. Provisioning circuitry 122 detectsinstantiated VNE 103 that is without provisioning link 133. Provisioningcircuitry 122 translates the ID for VNE 103 into an Internet Protocol(IP) address and port. Network transceiver 121 uses the IP address/portto exchange network signaling with VNE 103 and establish provisioninglink 133. Establishing provisioning link 133 entails, authentication,authorization, encryption, tunneling, and/or the like.

Provisioning circuitry 122 identifies provisioning data for theinstantiated VNE. The provisioning data comprises operating software anddata. The operating software and data supports network element taskslike packet routing, user authorization, session control, serviceaccounting, and/or the like. Provisioning circuitry 122 typicallyprocesses the current VNE version and location (as indicated by the VNEitself or the network element information) to select the provisioningdata. Provisioning circuitry 122 transfers the provisioning data tonetwork transceiver 121 for delivery to the instantiated VNE over thenew provisioning link. Network transceiver 121 transfers the networkprovisioning data to the instantiated VNE over the new provisioninglink. For example, provisioning circuitry 122 may enter a data structurewith the VNE type and VNE version for VNE 103 to yield a specific packetinspection software update. The near real-time establishment of theprovisioning links 131-135 allows provisioning circuitry 122 tosynchronize VNE software versions for VNEs 101-105 across VNE types andgeographic regions.

For example, provisioning circuitry 122 might synchronize routersoftware in packet gateways in the east coast region. As soon as a newpacket gateway is instantiated in the east coast region, provisioningcircuitry 122 detects and synchs the new gateway VNE to the desiredrouter software version. As soon as new router software versions arereleased for the packet gateways in the east coast region, provisioningcircuitry 122 has provisioning links ready to immediately installsynchronized software updates in the gateway VNEs.

Advantageously, provisioning system 120 efficiently and effectivelyprovisions VNEs 101-105 in wireless communication network 100.

FIG. 2 illustrates the operation of provisioning system 120 to provisionVNEs 101-105 in wireless communication network 100. Network transceiver121 receives network element information from wireless communicationnetwork 100 that characterizes VNEs 101-105 (201). Provisioningcircuitry 122 processes the network element information to detect anyactive VNEs 101-105 that do not have their corresponding provisioninglinks 131-135 (201). Provisioning circuitry 122 processes the networkelement information to detect any inactive VNEs 101-105 that still havetheir corresponding provisioning links 131-135 (201). When an active VNEis detected that does not have a provisioning link (203), provisioningcircuitry 122 determines a network address for the VNE (203).Provisioning circuitry 122 exchanges network signaling and the networkaddress with network transceiver 121 to initiate a provisioning link forthe new VNE (204). Network transceiver 122 exchanges the networksignaling with the VNF using the network address to establish theprovisioning link (205). Provisioning circuitry 122 transfersprovisioning data to network transceiver 121 for delivery to the VNEover the provisioning link (206). Network transceiver 121 transfers thenetwork provisioning data to the virtual network element over theprovisioning link (207). When an inactive VNE is detected that has aprovisioning link (208), then provisioning circuitry 122 terminates theprovisioning link for the inactive VNE (209).

FIG. 3 illustrates the operation of wireless communication network 100to provision VNE 101. VNE controller 115 instantiates VNE 101. VNEcontroller 115 then transfers network element information to networktransceiver 121 that characterizes VNE 101 including its VNE identifierand instantiation status. The network element information may alsoindicate VNE address, VNE DNS, VNE type, VNE version, VNE location, andthe like. Network transceiver 121 transfers the network elementinformation to provisioning circuitry 122. Provisioning circuitry 122processes the network element information to detect active VNE 101 andto determine if provisioning link 131 has been established for VNE 101.

In this case, VNE 101 is active but does not yet have provisioning link131, so provisioning circuitry 122 determines a network address for VNE101. Provisioning circuitry 122 may translate the VNE ID from thenetwork element information into the VNE network address. Provisioningcircuitry 122 exchanges network signaling and the network address withnetwork transceiver 121 to initiate provisioning link 131. Networktransceiver 121 exchanges the network signaling with VNF 101 using thenetwork address to establish provisioning link 131.

Provisioning circuitry 122 selects and transfers provisioning data tonetwork transceiver 121 for delivery to the VNE 101 over provisioninglink 131. Network transceiver 121 transfers the provisioning data to VNE101 over provisioning link 131. For example, provisioning circuitry 122may synchronize VNE software for VNE 101 with the VNE software versionfor VNE 102. Some of the UEs then exchange wireless user with wirelessaccess point 107 for a data service like internet access or socialnetworking. Wireless access point 107 exchanges the user data for thedata service with VNE 101. VNE exchanges the user data for the dataservice with other VNEs or systems (not shown).

In response to the instantiation of VNE 103, provisioning circuitry 122transfers more provisioning data to network transceiver 121 for deliveryto the VNE 101. Network transceiver 121 transfers the provisioning datato VNE 101 over provisioning link 131. For example, provisioningcircuitry 122 may synchronize the VNE software for VNEs 101-102 with thenewer VNE software version for new VNE 103. The UEs exchange wirelessuser data with wireless access point 107 for the data service. Wirelessaccess point 107 exchanges the user data with VNE 101, and VNE 101exchanges the user data for the data service the other systems.

VNE controller 115 de-instantiates VNE 101. VNE controller 115 thentransfers network element information to network transceiver 121 thatcharacterizes VNE 101 including its VNE identifier and de-instantiationstatus. Provisioning circuitry 122 processes the network elementinformation to detect that VNE 101 is inactive and to determine thatprovisioning link 131 should be terminated. Provisioning circuitry 122terminates provisioning link 131—typically by deleting communicationcontext data from memory and by releasing the processing resources thatwere serving provisioning link 131. [33] FIG. 4 illustrates wirelesscommunication network 400 that provisions Network FunctionVirtualization (NFV) Virtual Network Functions (VNFs) 401-402. Wirelesscommunication network 400 comprises UE/Radios 407, NFV Infrastructures(NFVIs) 410-411, and provisioning system 420. UE/Radios 407 comprisesUEs and wireless access points that are wirelessly linked. The wirelessaccess points are linked to NFVIs 410-411.

NFVIs 410-411 comprise computer hardware like microprocessors, memories,bus interfaces, and network transceivers. The microprocessors, memories,bus interfaces, and network transceivers store and execute hardwaredrivers. The memories store operating systems, virtual components, VNFs401-402, and MANO 415-416. The virtual components comprise hypervisormodules, virtual switches, virtual machines, and the like. Themicroprocessors execute the operating systems, virtual components, VNFs401-402, and MANO 415-416.

Provisioning system 420 comprises computer hardware 421 that comprisesnetwork transceivers, microprocessors, memories, and bus interfaces. Thenetwork transceivers, microprocessors, memories, and bus interfacesstore and execute hardware drivers. The memories store operating systemsand provisioning applications 422. The microprocessors execute theoperating systems and provisioning applications 422 to provision VNFs401-402.

VNFs 401-402 may be active/instantiated or inactive/de-instantiated.Active/instantiated VNFs 401-402 have on-going computer hardware andsoftware that are allocated for their operation.Inactive/de-instantiated VNFs 401-402 do not have computer hardware andsoftware allocated for their operation. Exemplary VNF 401-405 comprise5GC AMF, 5GC SMF, 5GC UPF, 5GNR RRC, 5GNR SDAP, 5GNR PDCP, SDNapplication, SDN controller, SDN data machine, LTE MME, LTE SGW, LTERRC, LTE PDCP, and/or the like.

In NFVIs 410-411, the Operational Support Systems (OSSs) direct theirslice controllers to implement new network slices that include VNFs401-402. The slice controllers direct MANO 415-416 to instantiate VNFs401-402 to serve the new network slices. MANO 415-416 directs theoperating systems in NFVIs 410-411 to instantiate VNFs 401-402. The UEswirelessly exchange data and signaling with the wireless access pointsin UE/Radios 407. The wireless access points exchange corresponding dataand signaling with VNFs 401-402. VNFs 401-402 exchange correspondingdata and signaling with external systems like conferencing servers andmachine controllers.

MANO 415-416 transfers VNF information that characterizes VNFs 401-402to provisioning applications 422. Provisioning applications 422 maintaindata structures that associates VNF addresses, VNF links, VNF types, VNFregions, VNF versions, and the like. Provisioning applications 422compare incoming network element information to the data structures inreal-time to detect any active VNFs 401-402 that do not haveprovisioning links. Provisioning applications 422 compare the incomingnetwork element information to the data structures in real-time todetect any inactive VNFs 401-402 that have provisioning links.

For newly active VNFs 401-402 that do not yet have provisioning links,provisioning applications 422 determine network addresses for the VNFsby translating VNF names into IP addresses. Provisioning applications422 exchange network signaling with active VNFs 401-402 using the IPaddresses to establish the provisioning links. Establishing theprovisioning links entails provisioning applications 422 and VNFs401-402 performing authentication, authorization, encryption, andtunneling.

Provisioning applications 422 identify provisioning data for new VNFs401-402. The provisioning data comprises software and/or data thatdirects the operation of VNFs like AMF, SMF, UPF, RRC, SDAP, PDCP,and/or the like. For example, provisioning applications 422 may enter adata structure with the VNF type, version, and region to yield theappropriate AMF software update. Provisioning applications 422 transferthe provisioning data to new VNFs 401-402.

In NFVIs 410-411, the OSS direct their slice controllers to terminatethe network slices that include VNFs 401-402. The slice controllersdirect MANO 415-416 to de-instantiate VNFs 401-402 that served thenetwork slices. MANO 415-416 directs the operating systems in NFVIs410-411 to de-instantiate VNFs 401-402. VNFs 401-402 no longer exchangedata and signaling for the data services. MANO 415-416 transfers VNFinformation that characterizes VNFs 401-402 to provisioning applications422. Provisioning applications 422 compare the incoming VNF informationto detect any inactive VNFs 401-402 that have provisioning links.Provisioning applications 422 terminate any active provisioning linksfor inactive VNFs 401-402 and updates the data structures.

FIG. 5 illustrates virtual network element provisioning system 520 toprovision virtual network elements 501 in wireless communication network500. Wireless communication network 500 comprises virtual networkelements 501 and orchestration 515. Virtual network element provisioningsystem 520 comprises Network Interface Card (NIC) 521, and provisioningcircuitry 522. Provisioning circuitry 522 comprises memories 523 andmicroprocessors 524. Memories 523 store an operating system (OS),provisioning application, provisioning data database (DB),synchronization database, VNE database, and link database.Microprocessors 524 execute the operating system and provisioningapplication to maintain the databases and transfer the provisioning datato virtual network elements 501 as described herein.

FIG. 6 illustrates the operation of virtual network element provisioningsystem 520 to provision virtual network elements 501 in wirelesscommunication network 500. In a first operation, orchestration 515instantiates a new VNE in virtual network elements 501. In a secondoperation, orchestration 515 notifies the provisioning application ofthe new VNE. In a third operation, the provisioning applicationtransfers the new VNE ID to the VNE DB to yield a “no VNE” result. In afourth operation, the VNE DB returns the negative VNE result to theprovisioning application. In a fifth operation, the provisioningapplication transfers the new VNE ID to the link DB to yield a “no link”result. In a sixth operation, the link DB returns the negative linkresult for the new VNE to the provisioning application. In a seventhoperation, the provisioning application establishes a provisioning linkwith the new VNE in virtual network elements 501.

In an eighth operation, the provisioning application transfers new VNEmetadata to the synch DB to yield a provisioning data version for thenew VNE. In a ninth operation, the synch DB returns a synchronizedprovisioning data version for the new VNE to the provisioningapplication. In a tenth operation, the provisioning applicationtransfers the synchronized provisioning data version to the provisioningdata DB to yield the provisioning data for the new VNE. In an eleventhoperation, the provisioning data DB returns the synchronizedprovisioning data for the new VNE to the provisioning application. In atwelfth operation, the provisioning application transfers thesynchronized provisioning data to the new VNE in virtual networkelements 501.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose wireless networkprovisioning circuitry to efficiently and effectively provision virtualnetwork elements. The computer hardware comprises processing circuitrylike CPUs, DSPs, GPUs, transceivers, bus circuitry, and memory. To formthese computer hardware structures, semiconductors like silicon orgermanium are positively and negatively doped to form transistors. Thedoping comprises ions like boron or phosphorus that are embedded withinthe semiconductor material. The transistors and other electronicstructures like capacitors and resistors are arranged and metallicallyconnected within the semiconductor to form devices like logic circuityand storage registers. The logic circuitry and storage registers arearranged to form larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose wireless networkprovisioning circuitry to efficiently and effectively provision virtualnetwork elements.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless communicationnetwork that comprises network circuitry which hosts a Virtual NetworkFunction (VNF), the method comprising: a VNF controller instantiatingthe VNF in the network circuitry and responsively transferringinstantiation information for the VNF to provisioning circuitry; theprovisioning circuitry receiving the instantiation information for theVNF and responsively establishing a provisioning data link to the VNFand transferring network provisioning data to the VNF over theprovisioning data link; the VNF controller de-instantiating the VNF inthe network circuitry and responsively transferring de-instantiationinformation for the VNF to the provisioning circuitry; and theprovisioning circuitry receiving the de-instantiation information forthe VNF and responsively terminating the provisioning data link to theVNF.
 2. The method of claim 1 wherein the network circuitry comprises aNetwork Function Virtualization Infrastructure (NFVI).
 3. The method ofclaim 1 wherein the VNF controller instantiating the VNF in the networkcircuitry and responsively transferring the instantiation informationfor the VNF to the provisioning circuitry comprises a Network FunctionVirtualization Management and Orchestration (NFV MANO) computerinstantiating the VNF in a Network Function VirtualizationInfrastructure (NFVI) and responsively transferring the instantiationinformation for the VNF to the provisioning circuitry.
 4. The method ofclaim 1 wherein the provisioning circuitry transferring the networkprovisioning data to the VNF over the provisioning data link comprisessynchronizing the VNF with other VNFs.
 5. The method of claim 1 wherein:the network circuitry comprises a Network Function VirtualizationInfrastructure (NFVI); the VNF controller instantiating the VNF in thenetwork circuitry and responsively transferring the instantiationinformation for the VNF to the provisioning circuitry comprises aNetwork Function Virtualization Management and Orchestration (NFV MANO)computer instantiating the VNF in the NFVI and responsively transferringthe instantiation information for the VNF to the provisioning circuitry;and the provisioning circuitry transferring the network provisioningdata to the VNF over the provisioning data link comprises synchronizingthe VNF with other VNFs.
 6. The method of claim 1 wherein the VNFcomprises an Access and Mobility Management Function (AMF).
 7. Themethod of claim 1 wherein the VNF comprises a Session ManagementFunction (SMF).
 8. The method of claim 1 wherein the VNF comprises aUser Plane Function (UPF),
 9. The method of claim 1 wherein the VNFcomprises a Radio Access Network (RAN) component.
 10. The method ofclaim 1 wherein the VNF comprises a Software Defined Network (SDN)controller.
 11. A wireless communication network that comprises networkcircuitry which hosts a Virtual Network Function (VNF), the wirelesscommunication network comprising: a VNF controller configured toinstantiate the VNF in the network circuitry and responsively transferinstantiation information for the VNF to provisioning circuitry; theprovisioning circuitry configured to receive the instantiationinformation for the VNF and responsively establish a provisioning datalink to the VNF and transfer network provisioning data to the VNF overthe provisioning data link; the VNF controller configured tode-instantiate the VNF in the network circuitry and responsivelytransfer de-instantiation information for the VNF to the provisioningcircuitry; and the provisioning circuitry configured to receive thede-instantiation information for the VNF and responsively terminate theprovisioning data link to the VNF.
 12. The wireless communicationnetwork of claim 11 wherein the network circuitry comprises a NetworkFunction Virtualization Infrastructure (NFVI).
 13. The wirelesscommunication network of claim 11 wherein the VNF controller comprises aNetwork Function Virtualization Management and Orchestration (NFV MANO)computer configured to instantiate the VNF in a Network FunctionVirtualization Infrastructure (NFVI) and responsively transfer theinstantiation information for the VNF to the provisioning circuitry. 14.The wireless communication network of claim 11 wherein the provisioningcircuitry is configured to synchronize the VNF with other VNFs over theprovisioning data link.
 15. The wireless communication network of claim11 wherein: the network circuitry comprises a Network FunctionVirtualization Infrastructure (NFVI); the VNF controller comprises aNetwork Function Virtualization Management and Orchestration (NFV MANO)computer configured to instantiate the VNF in the NFVI and responsivelytransfer the instantiation information for the VNF to the provisioningcircuitry; and the provisioning circuitry is configured to synchronizethe VNF with other VNFs by transferring the network provisioning data tothe VNF over the provisioning data link.
 16. The wireless communicationnetwork of claim 11 wherein the VNF comprises an Access and MobilityManagement Function (AMF).
 17. The wireless communication network ofclaim 11 wherein the VNF comprises a Session Management Function (SMF).18. The wireless communication network of claim 11 wherein the VNFcomprises a User Plane Function (UPF),
 19. The wireless communicationnetwork of claim 11 wherein the VNF comprises a Radio Access Network(RAN) component.
 20. The wireless communication network of claim 11wherein the VNF comprises a Software Defined Network (SDN) controller.